Skip to content

Remove dev prefix in config-remote-sync when resource is renamed#4919

Merged
ilyakuz-db merged 1 commit intomainfrom
remove-dev-prefix-config-sync
Apr 10, 2026
Merged

Remove dev prefix in config-remote-sync when resource is renamed#4919
ilyakuz-db merged 1 commit intomainfrom
remove-dev-prefix-config-sync

Conversation

@ilyakuz-db
Copy link
Copy Markdown
Contributor

@ilyakuz-db ilyakuz-db commented Apr 8, 2026

Changes

Remove current dev-prefix when config-remote-sync applies resource name changes to avoid duplicating it in the config

Why

If we don't do that users always need to remove dev prefix manually even for simple renames like [prefix] foo_1 => [prefix] foo_2. If they don't do it that leads to job names like this: [dev username] [dev username] my_job

Tests

Update acceptance tests

@ilyakuz-db ilyakuz-db changed the title Strip dev prefix during renames Remove dev prefix in config-remote-sync when resource is renamed Apr 8, 2026
@ilyakuz-db ilyakuz-db marked this pull request as ready for review April 8, 2026 16:09
When syncing remote resource changes back to config YAML, strip the
dev name prefix (e.g. "[dev user] ") from job, pipeline, and dashboard
names so only the unprefixed name is written to the config.

Co-authored-by: Isaac
@ilyakuz-db ilyakuz-db force-pushed the remove-dev-prefix-config-sync branch from 8447095 to bd49741 Compare April 10, 2026 10:59
@ilyakuz-db ilyakuz-db added this pull request to the merge queue Apr 10, 2026
Merged via the queue into main with commit 048a854 Apr 10, 2026
19 checks passed
@ilyakuz-db ilyakuz-db deleted the remove-dev-prefix-config-sync branch April 10, 2026 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants